snmpEngineBoots stores the number of times the SNMP Engine has initialized (on switch reboot or SNMP restart the value will increment). The value should always be a positive number in the range of 1-2147483647. Due to some internal error snmpEngineBoots read got failed. The reason for failure can be identified from the error code. The errors are self-correcting. A wrong read will reset the value to 1. The reset will not cause any issue in the system and system will continue to work in the expected way. The Error condition and corresponding error codes are as follows. -1: Parameter not valid -2: Object type not valid -3: Not used -4: Device could not be opened -5: Object was not found -6: Error occurred attempting to add an object -7: Object is read only -8: Device is not valid -9: Read error occurred -10: Seek error occurred -11: Device error occurred during the operation -12: Device contains no objects -13: Device is full -14: EOF was encountered -15: No EOI object found -16: An internal routine was passed a bad file descriptor
It is indeed a failure. But this do not cause any change in the behavior of SNMP or the switch. Only change after this will be the reset of the boot counter. If the counter value is being closely monitored or used, then the user can change the value with the recent value using command "configure snmpv3 engine-boots <value>". In the case of write error, the previous value is even provided in the warning message. Call for RMA is required only when the failure is frequent. That is multiple failures due to read, seek or device error (Error types can be identified from the return value). This kind of multiple failure in the same switch can be called for an RMA, since it is not the expected behavior from our hardware.
Warning
An internal read error (Error code %ecode%) occurred while reading snmpEngineBoots value from non-volatile memory.
| Name | Type |
|---|---|
| ecode | sInt32 |